home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
sfued105.zip
/
README17.SFU
< prev
next >
Wrap
Text File
|
1991-12-06
|
14KB
|
259 lines
StormFront User Editor for the Opus-CBCS
Programmed by Kevin Silcox
December 6, 1991
Disclaimer
----------
This software is available "AS IS". It is not guaranteed to work at
all. If it trashes your system or ruins your life, you have been warned.
I am not responsible for any damages incurred from the use or misuse of
this software. There is also no fee to use this software.
You will have to get by without any real documentation until I, or
someone else write some for this program. If you know Opus and how it
works, then this program should be pretty much self-explanatory as far
as what the actual changes to the user database do. So for now, there's
only a brief description of how to use the actual functions of the program.
Even though SFUE isn't the most user-friendly program, I think that its
flexibility and simplicity (well, in some ways) is worth the struggle
you may go through when you first start to use it. Enjoy!
-------------------------------------------------
This version: 1.05 ---> For Opus v1.7x
**-- Version numbers with a lowercase letter are beta versions. --**
Requires approximately 80K of Available RAM. Requires
more if using the Sort option (based on number of records
in your database --> about 28 bytes for each record).
This program is for maintaining the user database used with
Opus. It is capable of adding users to the USER.DAT file, marking
them to be ReUsed, Purged, Normal, and even Removing users marked
to be Purged (Zap), along with many other features.
The program accepts a command-line argument for local and non-
local use. The arguments are as follows: -M for Mono, -C for Color,
-D for DOS Output, -B for BIOS Writes, -Z to Zap the database, or
-F to specify which User Database file to use.
The -M and -C options are only to force the memory address for the
direct-screen writes if the program doesn't recognize the correct video
mode. If no arguments are entered, the program will AutoDetect which
video mode to use for the direct-screen writes. Entering an argument
other than those arguments listed will display a brief help screen.
The -F allows you to specify the name of the User Database file
that you want to use instead of the default USER.DAT. If you specify
just the full path without a filename, USER.DAT will be assumed (you
must have a "\" after the path though).
**==--==**
In the lower right-hand corner of the User Screen are the commands
that are available in all ScreenSections. Below is a brief description
of what they do:
R) Record Number: This allows you to go to a specific record number
within the database.
!) User Status: This allows you to modify the status of a user's
record. The Status can be one of the following:
Normal: This is a normal record.
Reuse : As new users are added, they will be placed in records
marked with this status instead of being added to the
end of the database.
Purge : This means that if you use the Zap function, the record
will be removed from the database. Also used by OMAN.
Update ID : This will update the caller ID number but should only be
used if the caller_ID is all zero's.
*) Utilities: This is for maintaining the database. These are:
Adduser: If you need to add a user, this is what you'll use.
It has gives you the option of just adding a record
at the end of the database, or searching for a record
marked with the "Reuse" status. If you choose to
search for a record to Reuse, and there is a record
marked with the Reuse status, then that record will be
cleared of its information and you may start entering
the new user information in that record.
Global : Allows you to make certain changes to specific (or all)
users. You may specify to set only a certain privilege
level, or the default is all records (record #1 will
NOT be touched). There are also sub-levels that I
don't have time to go into.
-=***=-
I feel that the options for changing Keys and Sections
may cause some confusion. With those two options there
are 4 sub-options [Exact/Set/Toggle/Unselect]:
Exact: Set each user to exactly the keys you
specify. If you only select the 'A' key,
that's the only key the users' will have
no matter what they started out with.
Set: All keys you specify will be turned ON for
each user.
Toggle: Exactly what it says... If you select the 'A'
key each users' keys will be set to the
opposite it started out as.
Unselect: The opposite of Set. It will make sure each
key you select is turned OFF.
Search : This allows you to search certain fields for a string.
It's useful for finding a specific user quickly among
other things.
sOrt : This will sort your database based on the keys you
select, and whether you select Ascending or Descending
order for each key. You may select up to two keys to
sort by.
** The sort is currently limited to about 1000 records
maximum until I get the time to write a different
sort routine other than the internal qsort(). **
sWap : This allows you to swap any two records with each other.
Report : This generates a report for all users and sends it either
to the Screen, Printer, or a File. You can Pause the
output by pressing 'P', or have an option to Abort by
pressing 'ESC'. You are asked several questions about
how the report should be, but I don't have the time to
go into detail explaining it...
Zap : This removes any records marked with the Purge status.
Also you can specify the number of days a user can go
without calling the system before he/she is removed from
the database. This option is also available from the
command-line. By default a file called USER.SAV will
be used to place any deleted records into. Currently
the only way for you to put a user from the USER.SAV
file back into the USER.DAT file is something like:
COPY /B USER.DAT+USER.SAV USER.DAT
That should re-build the database.
+/-) Change Record Number: You can use either the plus and minus keys
to increment/decrement the record number
respectively, or use the left and right arrow
keys to do the same thing. Home and End
will place you at the first and last records
respectively.
ESC) Quit: If you have made any changes to the current record without
going to another record, you will be asked if you want to
save the user information before exiting. Anytime you
change to another record, the current record is saved to
disk if it has been modified.
SPACE) (SpaceBar) ScrnSect: Changes the current Screen Section. The
active ScrnSect is displayed at the top of
the screen. The Screen Sections are at the
left side of each box border. A ScrnSect
must be active in order for its commands
to be active. Also when a ScrnSect is
active, the number next to the active box
will BLINK.
The ScrnSect can also be changed with the up
and down arrow keys to decrement/increment
the ScrnSect number respectively.
F9) DOS Shell: Exactly what it says. The User Editor is NOT swapped
out of memory.
**==--==**
I hope this is enough of a program description to get you familiar with
the program. For Opus v1.7x the ScrnSect is not the same as the "Section" in
Opus.
Currently this Editor doesn't contain an internal index updating function.
You will need to use the USERNDX program that is distributed with Opus v1.7x.
The Editor will call USERNDX when exiting whenever it thinks the Index needs
to be updated. USERNDX will only be called when you have made changes inside
the Editor that might change the NDX file. USERNDX must either be located in
the PATH, or in the same directory as your user database, or in your Opus Home
Directory.
------------------------------------------------------
***********************
* Report Information: *
***********************
**
Level of Detail Grouping (80-column output):
------------------------------------------------------
1:
A = User Record Number (Width = 5)
B = User Name (Width = 26)
C = Phone Number (Width = 15)
D = City, State (Width = 25)
--
2:
E = Street Address (Width = 26)
F = Answer to SysOp Question (Width = 43)
--
3:
G = SysOp Comment (Width = 44)
H = Birthdate (Width = 9)
I = Access Privilege (Width = 9)
--
4:
J = Keys (Width = 32)
K = Download:Upload Ratio (Width = 9)
L = Days Since Last Call (Width = 4)
M = Password (optional) (Width = 15)
------------------------------------------------------
**
Level of Detail Grouping (132-column output):
------------------------------------------------------
1:
A = User Record Number (Width = 5)
B = User Name (Width = 26)
C = Phone Number (Width = 15)
D = City, State (Width = 25)
E = Street Address (Width = 25)
F = Alias (Width = 20)
--
2:
G = Answer to SysOp Question (Width = 44)
H = SysOp Comment (Width = 45)
I = Birthdate (Width = 9)
J = Password (optional) (Width = 15)
--
3:
K = Access Privilege (Width = 9)
L = Keys (Width = 32)
M = Download:Upload Ratio (Width = 9)
N = Days Since Last Call (Width = 4)
O = First Call to System (Width = 11)
------------------------------------------------------
------------------------------------------------------
Thank You for taking your time to read this, and use my program.
If you have any comments or suggestions, I'd like to hear from you.
Please contact me if you have any problems with the program, or you
would like to see any added features. You may contact me (via NetMail)
at the phone number (or FidoNet Address) listed below. I also read the
NEWOPUS and MEADOW Echo's. The latest version of my software is also
available on my BBS. It may be requested with the magic name of "SFUE17"
for the Opus 1.7x version, and "SFUE11" for the Opus 1.1x version.
--=={ Kevin Silcox ------
SysOp of:
The StormFront BBS
in Orangevale, California
(916) 988-0407
FidoNet (1:203/407.0)
BBS Hours:
Conditionally 23 hours a day,
but definately between:
11:00 p.m. and 11:00 a.m
excluding National Mail Hour:
1:00 a.m to 2:00 a.m PST
Since this phone number is also my voice number for now, there may be
times when I pick up the phone instead of the computer. If this happens
I'll immediately try to force the BBS to answer the phone so you don't
have to call back. I'll try to make the line busy whenever I'm doing
something on the computer that would prevent me from forcing the BBS to
answer. Have fun!
Special Thanks to my Beta Test Team for making suggestions that have
increased the power (and flexibility) of SFUE, and especially for finding
those little critters that lurk around in most software!